. Knowing that, I can work around this for now, although
>>>> emacs+auctex probably won't be happy without --nonstop.
>>>> I updated the stand-alone ConTeXt a few minutes ago, so I'm up to date on
>>>> that.
>>>> Is this a bug introduced by some recent chang
>
> >> does create the .synctex file.
>
>
> >> The ConTeXt distribution version *does* create the file if --nonstop is
> >> *not* used. Knowing that, I can work around this for now, although
> >> emacs+auctex probably won't be happy without --nonstop.
>
>
that, I can work around this for now, although
>> emacs+auctex probably won't be happy without --nonstop.
>> I updated the stand-alone ConTeXt a few minutes ago, so I'm up to date on
>> that.
>> Is this a bug introduced by some recent change?
> it's more a feature
recent change?
it's more a feature
- Mikael S and i spend some time with editor/viewer combinations on
linux in order to find ways around the different synctex libs that they use
- as a result we could make most work ok
- we assume that synctex is set up in the document with
\setupsynctex
stopMPpage
>
> so a single path option (no picture)
>
> Hans
>
>
> Thank you so much for the sample examples
> it would be great to also make text select able in output pdf
> the third example currently does not work. di
ed, blue)
> > ;
> > \stopMPpage
> >
> > so a single path option (no picture)
> >
> > Hans
> >
> >
> > Thank you so much for the sample examples
> > it would be great to also make text select able in outpu
so a single path option (no picture)
Hans
Thank you so much for the sample examples
it would be great to also make text select able in output pdf
the third example currently does not work. did you mean you will add
this feature for next updates?
we're talking outlines so that is pat
e)
>
> Hans
>
Thank you so much for the sample examples
it would be great to also make text select able in output pdf
the third example currently does not work. did you mean you will add this
feature for next updates?
__
g examples that can
apply gradient colors to metapost paths.
how i can apply this cool feature to a piece of text?
i tried the code below but it does not produce any result.
\definecolor[Gleft] [h=9f9393]
\definecolor[Gright] [h=ff1aa4]
\startMPpage
picture Mytext;
Mytext := btex hello etex;
draw
hi all,
when i look at luametafun manual there are some intresting examples that can
apply gradient colors to metapost paths.
how i can apply this cool feature to a piece of text?
i tried the code below but it does not produce any result.
\definecolor[Gleft] [h=9f9393]
\definecolor[Gright] [h
s. You can
activate these ligatures as a font feature though (AFAIR
"latexhyphens", can’t find it…).
The name of the option has changes a few times and the current setting
is textcontrol=collapsehyphens.
Some editors and some fonts do automatical replacements.
In this case it could
that adds a
hairspace after or before the dash, since I don't like it to stick to
some letters like "o".
Generally, “we” try to reduce active characters as much as possible,
that’s why -- and --- usually /don’t/ produce en or em dashes. You can
activate these ligatures as a font feat
don't like it to stick to some letters like "o".
Generally, “we” try to reduce active characters as much as possible,
that’s why -- and --- usually /don’t/ produce en or em dashes. You can
activate these ligatures as a font feature though (AFAIR "latexhyphens",
can’t find
feature.
When I tried line correction, it never helped; probably I used it wrong
(e.g. around section titles).
linecorrection is older, textdisplay newer and both are mainly meant to
position boxed content (like images) in a way so that spacing looks
acceptable ... they are vboxes with spacing
{10}{20}
\blank[2*line]
\fakewords{10}{20}
\starttextdisplay
\fakeimage{4cm}{3cm}{6cm}{4cm}
\stoptextdisplay
\fakewords{10}{20}
\stoptext
Thank you!
And when would you suggest what?
A float I’d use only if I need caption/numbering or the floating feature.
When I tried line correction, it never
tures which in turn means that if
one uses svg as output format one has to specify every character with
possible abuse of a substitution feature that accesses it. So that is
no longer a real interesting option, unless of course one exports all
text as curves, just to be sure.
(I will extend general text
n in general. That said, as long as one sticks to reliable and
> clean code (plain svg) it should mostly work out.
>
> Text is another matter because svg dropped glyph support so now
> everything has to go through font features which in turn means that if
> one uses svg as output fo
clean code (plain svg) it should mostly work out.
Text is another matter because svg dropped glyph support so now
everything has to go through font features which in turn means that if
one uses svg as output format one has to specify every character with
possible abuse of a substitution feature tha
reate a line when 25 could be used. Then we can develop a method
> > to turn that mechanism off or circumvent it.
> > Quotation from https://www.w3.org/TR/jlreq:
> > In principle, when composing a line with ideographic (cl-19), hiragana
> > (cl-15) and katakana (cl-16) ch
that mechanism off or circumvent it.
> > Quotation from https://www.w3.org/TR/jlreq:
> > In principle, when composing a line with ideographic (cl-19), hiragana
> > (cl-15) and katakana (cl-16) characters, no extra spacing appears between
> > their character frame. This is call
thousands of lines of code, so have no idea how to break the
problem down to a minimal example. What does [entry not flushed] mean? What
kind of feature in my document do I need to search for that might explain why
this is appearing?
Here is the minimal code used in my index, as you see it isn
s of lines of code, so have no idea how to break the
problem down to a minimal example. What does [entry not flushed] mean? What
kind of feature in my document do I need to search for that might explain why
this is appearing?
Here is the minimal code used in my index, as you see it isn't showing
extra spacing appears between
> their character frame. This is called solid setting (see Figure 5).
>
> 1. ConTeXt has a mechanism to typeset Japanese texts.
>
> 2. There are flaws in the output it produces but this nothing which can't be
> fixed.
>
> 3. To fix th
not flushed] mean? What
kind of feature in my document do I need to search for that might explain why
this is appearing?
Here is the minimal code used in my index, as you see it isn't showing the
error, so something else in the document is causing it:
\setvalue{W3}{this is text for W3
t; > draw lmt_svg [
> > filename = "smile.svg"]
> > \stopMPcode
> > \stoptext
> >
> > also when i look at evenmore manual at page15, for font Abelone-FREE the
> gradients has rendered properly is there difference between renderi
e.svg"]
\stopMPcode
\stoptext
also when i look at evenmore manual at page15, for font Abelone-FREE the
gradients has rendered properly is there difference between rendering such
fonts and rendering SVGs?
if its a font feature how i can use this font features
d properly is there difference between rendering such
fonts and rendering SVGs?
if its a font feature how i can use this font features for my svg?
___
If your question is of interest to others as well, please ad
more or us to have a test option. Curvature detection is mostly a pdf
efficiency feature and normally users should rely on the default to work
okay.
Other new mp features are relative and absolute points which makes it
possible to define paths in a turtle graphics way (a bit like hlineto
and
see in my second example file japanese.tex there is a
font feature to create half sized parentheses etc. which isn't
supported yet by ConTeXt's mechanism for japanese and in case your
willing to improve it this should be taken
{\glyphslant 500 test \glyphslant \numericscaled2.0\glyphslant
test} test
test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight
test} test
\stoptext
The problem is that compact mode uses them to apply the slanted feature
without any manual use of the commands from a user
produces but this nothing which can't be
> fixed.
> 3. To fix the problems someone has to be passionate to fix them and we're
> willing to help here.
> As you can see in my second example file japanese.tex there is a font feature
> to create half sized parentheses
\glyphslant
test} test
test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight
test} test
\stoptext
The problem is that compact mode uses them to apply the slanted feature
without any manual use of the commands from a user.
\enableexperiments[fonts.compact]
\definefontfamily
With current latest (2024.02.27 09:21), LuaTeX gets boldened and slanted
for regular (but the other fonts cannot inherit the wider feature and
wider will not mix with boldened-30 [even when specified]).
For some reason, LMTX from current latest cannot get slanted and
boldened-30 (but it mixes the inherited
On 04/03/2024 09:08, Hans Hagen via ntg-context wrote:
You're missing the fact that the font has an issue. I can add a
workaround, assuming that (as often) issues become features.
A useful feature, if it not already exists, might be a tool to detect
whether a font has issues. That can
(but the other fonts cannot inherit the wider feature and
wider will not mix with boldened-30 [even when specified]).
For some reason, LMTX from current latest cannot get slanted and
boldened-30 (but it mixes the inherited wider feature in all fonts).
This began to behave differently in latest from
cond example file japanese.tex there is a font
feature to create half sized parentheses etc. which isn't supported yet
by ConTeXt's mechanism for japanese and in case your willing to improve
it this should be taken care of as well.
Wolfgang
\definefontfeature [halt] [halt=yes]
\starttext
\s
Am 22.02.24 um 18:35 schrieb Hans Hagen via ntg-context:
On 2/21/2024 7:47 PM, Henning Hraban Ramm wrote:
(I’m sure I already used that somewhere… Must document…)
ok, new feature dedicated to Hraban ... who then of course has to
document it.
This is nice.
Thank you, will do.
(Actually I’m
withdots withcolor "red";
setbounds currentpicture to OverlayBox;
\stopuseMPgraphic
Thank you!
(I’m sure I already used that somewhere… Must document…)
ok, new feature dedicated to Hraban ... who then of courese has to
document it.
\starttext
\starttabulate
\FL[1,2] % linef
too, but 2 doesn't
\protect
then I get the spacing I want.
Q2: \c_strc_itemgroups_spacing_mode seems to be an undocumented "feature".
Is there a "documented" way of making the unwanted blank line
go away, without introducing unwanted blank lines
s \HF[] documented anywhere? If so, can someone point me to that/those
>> document(s)?
>> Perhaps an answer to Q2 will answer this one too, but in case it doesn't...
>> When using Wichura's \BeginTable ... \EndTable macros, I occasionally
>> use the \\+nm feature to add
ed in a math context?
It was indeed used in a math context. Unfortunately, that knowledge
doesn't bring me any closer to finding the documentation. (Which gets me
back to my learning curve. :-)
>> Perhaps an answer to Q2 will answer this one too, but in case it doesn't...
>> When using
document(s)?
>
>
>
> Perhaps an answer to Q2 will answer this one too, but in case it doesn't...
>
> When using Wichura's \BeginTable ... \EndTable macros, I occasionally
> use the \\+nm feature to add n points above the current line and/or m
> points below the current li
it doesn't...
When using Wichura's \BeginTable ... \EndTable macros, I occasionally
use the \\+nm feature to add n points above the current line and/or m
points below the current line.
Q3: Does ConTexT's \starttable ... \endtable have this feature?
If so, how does one access this feature?
Probabl
document(s)?
Perhaps an answer to Q2 will answer this one too, but in case it doesn't...
When using Wichura's \BeginTable ... \EndTable macros, I occasionally
use the \\+nm feature to add n points above the current line and/or m
points below the current line.
Q3: Does ConTexT's \starttable ...
/manuals/musings.pdf#page=96 might
explain why Lua(Meta)TeX is slower.
Other chapters in that document from Hans might give you some insight on
the reasons why LMTX has to pay a price for being more feature-rich. I
got such impression when I read it.
Just in case it might help,
In comparison to LaTeX
Lua(Meta)TeX is slower.
Other chapters in that document from Hans might give you some insight on
the reasons why LMTX has to pay a price for being more feature-rich. I
got such impression when I read it.
Just in case it might
y to do it.
>> Can someone either enlighten me on either
>> (a) the Right ConTeXt Way to do this, or
>> (b) a document that would tell me this, if I knew to read it?
>> I've looked in the wiki, the not-so-short intro to ConTeXt, and "ConTeXt:
>> an excursion&qu
ten me on either
(a) the Right ConTeXt Way to do this, or
(b) a document that would tell me this, if I knew to read it?
I've looked in the wiki, the not-so-short intro to ConTeXt, and "ConTeXt:
an excursion" with no luck.
Hi Jim,
such a feature exists only to suppress paragraph indenta
, a écrit :
\setupmathematics[textdistance=.25em plus .1em minus .1em]
Hm, I can make it optional (engine feature then) but will discuss it
with Mikael first.
Hans
-
Hans Hagen | PRAGMA ADE
e and \outlined
[…]
which of course you then will wikify ...
Of course, I’ll wikify this new feature in ConTeXt.
As it might help other users, I‘m happy to help.
I’ll have to wait until I test \namedgoto myself, because I don’t get
how \namedgoto may differ from \goto.
it obeys an interactio
my way.
> […]
> which already might help you. To make it easier I'll add \namedgoto do
> that one can say:
> […]
> I'll also add \outline and \outlined
> […]
> which of course you then will wikify ...
Of course, I’ll wikify this new feature in ConTeXt.
As it might help other users,
torized or ... seen all kind of
> variants) ... officially a rendering should listen to some keys that relate
> to it but this is not always the case
>
> (part of the problem is, i think, that esp for check fields a bugs or
> behaviour has become a feature which makes it kin dof incons
44:38 AM
Subject [NTG-context] Re: Toggling the symbol for the zero-width joiner and
related Unicode control characters
(It seems he never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surprising.
s do other Arabic fonts.
(It seems he never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surprising.)
I admit that I don't follow what happens with xetex (they changed the
rendere at so
never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surprising.)
But therein lies the problem: ConTeXt shows the rendering by default, and we
need to turn it off. Since most non-Latin typo
. So not "an inconsistent mess" -- at least not as far as
Arabic-script typography is concerned.
(Yes, for the upcoming Husayni I can add a font feature that does the trick,
but that will be an exception to the rule.)
Perhaps others who use Arabic-script or Indic, etc., c
somewhere.
If that’s not obvious or a known feature, I’ll try to come up with a
minimal example – I encountered it within a columnset, but don’t know if
it’s related to columns or my own dimensions (\measure).
Hraban
03. Thanks
in advance.
bug or feature: just something not done yet (there are probably a few
more places) ... i added it (no upload)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat
Hi, list. The following fails with a "Missing number, treated as zero"
error prompt:
\starttext
\expandedrepeat2{\expandedrepeat2{\the\numexpression#I+#P\relax\ }}
\stoptext
OTOH, \numexpr works seamlessly. Tested on ConTeXt 2023.09.03 19:03. Thanks
in advance.
Best regards,
Jairo
On 9/3/23 16:02, Henning Hraban Ramm wrote:
> Am 03.09.23 um 13:03 schrieb Pablo Rodriguez:
> [...]
> While I don’t know what’s missing under the hood, I think there’s just a
> “reference” key missing in \attachment or \setupattachment:
Many thanks for your reply, Hraban.
I’m afraid that
Am 03.09.23 um 13:03 schrieb Pablo Rodriguez:
On 9/3/23 12:46, Hans Hagen wrote:
On 9/3/2023 12:17 PM, Pablo Rodriguez wrote:
[...]
This basic implementation of GoToE links would be extremely helpful to
access embedded documents (believe it or not, this is something I
explain almost every week
On 9/3/23 12:46, Hans Hagen wrote:
> On 9/3/2023 12:17 PM, Pablo Rodriguez wrote:
>> [...]
>> This basic implementation of GoToE links would be extremely helpful to
>> access embedded documents (believe it or not, this is something I
>> explain almost every week at work).
>>
>> I would be happy to
On 9/3/2023 12:17 PM, Pablo Rodriguez wrote:
Hi Hans,
having attachments in PDF is very useful, but the vast majority of
people don’t know how to handle them (even with the attachment pane
displayed when Acrobat opens the document, or with file annotation).
It would be really useful to have a
Hi Hans,
having attachments in PDF is very useful, but the vast majority of
people don’t know how to handle them (even with the attachment pane
displayed when Acrobat opens the document, or with file annotation).
It would be really useful to have a link with destination that it would
open the
On 9/2/23 12:42, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 02.09.2023 um 12:35:
>> [...]
>> Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I
>> know I should know better, but I‘m stuck at this):
>>
>> \definefontfamily[mainface][rm][DejaVu Sans]
>>
Pablo Rodriguez schrieb am 02.09.2023 um 12:35:
[...]
Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I
know I should know better, but I‘m stuck at this):
\definefontfamily[mainface][rm][DejaVu Sans]
[sl≃style:bf]
You're using the wrong symbol (you have a math
On 9/2/23 12:18, Wolfgang Schuster wrote:
> Hans Hagen schrieb am 02.09.2023 um 11:53:
> [...]
>> in lpdf-lmt.lmt you can try:
>>
>> l 593
>>
>> tmsy = tmsy * sc
>>
>> l 610
>>
>> tmsy = tmsy * f_y_scale
>
> I get now with LMTX the same output as I get with MkIV, the slant stays
> the same for all
Hans Hagen schrieb am 02.09.2023 um 11:53:
On 9/2/2023 11:45 AM, Wolfgang Schuster wrote:
Pablo Rodriguez schrieb am 02.09.2023 um 10:25:
Dear list,
I have the following sample (using current latest from 2023.08.27
13:48):
\setupinteractionscreen[option=max]
On 9/2/2023 11:45 AM, Wolfgang Schuster wrote:
Pablo Rodriguez schrieb am 02.09.2023 um 10:25:
Dear list,
I have the following sample (using current latest from 2023.08.27 13:48):
\setupinteractionscreen[option=max]
\definefontfamily[maf][rm][DejaVu Sans]
[sl={style:tf,
Pablo Rodriguez schrieb am 02.09.2023 um 10:25:
Dear list,
I have the following sample (using current latest from 2023.08.27 13:48):
\setupinteractionscreen[option=max]
\definefontfamily[maf][rm][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt]
Dear list,
I have the following sample (using current latest from 2023.08.27 13:48):
\setupinteractionscreen[option=max]
\definefontfamily[maf][rm][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
Forwarded Message
Subject: Re: [NTG-context] Kerning feature not working
Date: Wed, 30 Aug 2023 22:17:43 +0200
From: Hans Hagen
To: Marcus Vinicius Mesquita
On 8/30/2023 9:37 PM, Marcus Vinicius Mesquita wrote:
Dear List
In the MWE below, the kerning feature works OK
Dear List
In the MWE below, the kerning feature works OK for ebgaramonditalic
but not for ebgaramondregular.
How do I fix it?
I'm using ConTeXt version: 2023.08.27 13:48
\startluacode
fonts.handlers.otf.addfeature {
name = "kernit",
type = "kern",
:
Dear gang,
For \addfeature and the like, a virtual font feature defined in terms of a CLD
local function behaves differently from other font features. MWE:
==
\startluacode
local function squeeze(tfmdata)
for k, v in next, tfmdata.characters do
v.width = 1.75 * (v.height or 0)
v.depth
On 8/20/2023 5:33 PM, Hamid,Idris wrote:
Dear gang,
For \addfeature and the like, a virtual font feature defined in terms of a CLD
local function behaves differently from other font features. MWE:
==
\startluacode
local function squeeze(tfmdata)
for k, v in next
Dear gang,
For \addfeature and the like, a virtual font feature defined in terms of a CLD
local function behaves differently from other font features. MWE:
==
\startluacode
local function squeeze(tfmdata)
for k, v in next, tfmdata.characters do
v.width = 1.75 * (v.height
requires \sc because it
provides a separate file for smallcaps but no smcp feature.
ConTeXt has a command which can be used to check whether the current
active font provides the smcp feature but the recommended way is to
choose a font which supports to method (\sc or \setsmallcaps) which is
used
}}
So on the wiki we should say that \sc is a deprecated/legacy command
that no longer makes sense in an opentype-features world. New users
should no longer use it.
It depends on the font, e.g. Latin Modern still requires \sc because it
provides a separate file for smallcaps but no smcp feature
makes sense in an opentype-features world. New users
should no longer use it.
It depends on the font, e.g. Latin Modern still requires \sc because it
provides a separate file for smallcaps but no smcp feature.
ConTeXt has a command which can be used to check whether the current
active font
Many thanks, Pablo. Yes, you are right. As mentioned in the reply to Wolfgang,
will edit the wiki to reflect the legacy\deprecated status of \sc.
As for grep: Normally I use the nice "find in files" feature of Notepad++ -)
Am editing the wiki and have moved the original link to the mo
styles that have the smcp feature, but I don't like having
to redefine a system command.
So the questions are:
1) Is there a recommended\better way to get \sc to work across all styles?
\setupbodyfont[pagella]
\starttext
\tf Upright, \it Italic, \bf Bold and \bi Bolditalic
\style[style
\sc{\addff{smallcaps}}
This works for all styles that have the smcp feature, but I don't like
having to redefine a system command.
So the questions are:
1) Is there a recommended\better way to get \sc to work across all
styles?
\setupbodyfont[pagella]
\starttext
\tf Upright, \it Italic
for all styles that have the smcp feature, but I don't like having
to redefine a system command.
So the questions are:
1) Is there a recommended\better way to get \sc to work across all styles?
2) Are there any edits you would recommend to the above typescript template?
Once we're clear
of view. Nothing else.
>>
>> I have no clue of what you talk about here.
>>
>>>
>>> from the TeXbook 380-381
>>>
>>> «\obeylines doesn’t say ‘\def^^M{\par}’, so we must make any desired
>>> changes to
>>> \par before invoking \obeyl
> > > changes a
> > > space to category 12; but the \tt font has the character ‘␣’ in the
> > > ⟨space⟩ position, so we
> > > don’t really want ␣12 . (3) The \obeyspaces macro in Appendix B merely
> > > changes the
> > > ⟨space⟩ character to cate
macro in Appendix B merely
> > changes the
> > ⟨space⟩ character to category 13; active character ␣13 has been defined to
> > be the same
> > as \space, a macro that expands to ␣10 . This is usually what is desired;
> > for example,
> > it means
but the \tt font has the character ‘␣’ in the ⟨space⟩
> > position, so we
> > don’t really want ␣12 . (3) The \obeyspaces macro in Appendix B merely
> > changes the
> > ⟨space⟩ character to category 13; active character ␣13 has been defined to
> > be the same
>
is usually what is desired; for
> example,
> it means that spaces in constructions like ‘\hbox to 10 pt {...}’ won’t cause
> any
> trouble. But in our application it has an undesirable effect, because it
> produces spaces
> that are affected by the space factor. To defeat this feat
but Hans suggestion to provide a hook which can be used to
re-enable the feature, e.g.
\startsetups [typing:mine]
\setbreakpoints[compound]
\stopsetups
\setuptyping [CUSTOM] [setups=typing:mine]
The only flaw I can see in the suggestion is the use
,
it means that spaces in constructions like ‘\hbox to 10 pt {...}’ won’t cause
any
trouble. But in our application it has an undesirable effect, because it
produces spaces
that are affected by the space factor. To defeat this feature, it’s necessary
either to
say \frenchspacing or to redefine ␣13
e 12pt roman
%D bodyfont.
-)
> well, in type-imp-latinmodern.mkiv i can find 'designsize' ... you're
> not relying on some gpt driven search machine are you?
No just the search files feature in Notepad++ -)
Ok, looking at type-imp-latinmodern.mkiv, under latin-modern-designsize, I see
base,
mirror and -scale or scale,
mirror and -scale or scale
},
},
}
end
end
end
-- in principle one can have some extra parameters for shifts but this
-- is suboptimal anyway and only meant for minion
local function in
This thread about downsampling external images on the fly is a really helpful
feature! Thanks, Hraban for sharing the code!
I was wondering if it was possible to downscale also raster images embedded in
pdf/svg files loaded via \externalfigure?
I found a ghostscript solution online
(https
defaultbrokenpenalty
\stopsetups
% we enable the use of expansion (this feature might become preset
% because we now delay setting the vectors anyway so less overhead)
\definefontfeature
[default]
[default]
[expansion=quality,
protrusion=quality,
itlc=yes]
% vertical expansion
\widowpenalty 1
\frozen\clubpenalty 1
\frozen\displaywidowpenalty 1
\frozen\brokenpenalty 0 % \defaultbrokenpenalty
\stopsetups
% we enable the use of expansion (this feature might become preset
% because we now delay setting the vectors anyway so less
% \defaultbrokenpenalty
\stopsetups
% we enable the use of expansion (this feature might become preset
% because we now delay setting the vectors anyway so less overhead)
\definefontfeature
[default]
[default]
[expansion=quality,
protrusion=quality,
itlc=yes]
% vertical expansion
On 7/18/2023 4:12 PM, Hans Hagen wrote:
Hi,
In todays upload there is a follow up on a new feature that is already
present in the previous upload (but that was not yet advertised):
context --parallel test1.tex test2.tex test3.tex
context --parallel --pattern=test*.tex
context
Hi,
In todays upload there is a follow up on a new feature that is already
present in the previous upload (but that was not yet advertised):
context --parallel test1.tex test2.tex test3.tex
context --parallel --pattern=test*.tex
context --parallellist myfile.cmd (filters context
in these
containers. (It was when the mp to pdf conmverter showed up in context
mkii.) One or these now obsolete sub projects; it was kind of fun
anyway. Other experiments, like with saving positions (which originally
was a context feature that involved betweeen run dvi parsing with
dvipos) did make
?
> No, it's an independent feature of the linebreak mechanism. You can run
> this and see how it kicks in
>
> \starttext
>
> \definecolor[ttest][a=1,t=.5]
> \definecolor[rtest][a=1,t=.5,r=1]
>
> \dostepwiserecurse{80}{120}{1}{
> \startTEXpage[of
1 - 100 of 4821 matches
Mail list logo
